~~NOTRANS~~
~~Title: Using Dynamic/User Objects~~

With a dynamic object, we think of a dynamically created object that is available in the application without changing the application. Sometimes, it's useful to "inject" objects into your application and use such objects in your business logic. This use-case is already supported via [[jvx:server:lco:inject_objects|]]. The missing part is that it's not automatically possible to access such objects in your application. Sure, if you put an [[jvx:server:lco:actions|action]] in your LCO and a [[jvx:communication:calling_server_action|simple remote call]] in your [[vaadin:customize_application|custom application]], it'll be easy. But it's not guaranteed that you have a custom application. It's some work to extend the standard ProjX application. So this is not something to be done last minute.

To support this use-case, we have dynamic objects available via standard ProjX API. And here is it:

<file java>
public Object getDynamicContent(String pName);
</file>
The name is the important thing. By default, no dynamic objects exist, so the method will return null.

If want to use a custom dynamic object, write one, e.g.:

<file java>
public class DynamicUserContent extends AbstractDynamicContent
{
    @Override
    public String getContentName() 
    {
        return "userDetails";
    }

    @Override
    public Object getDynamicContent()
    {
        String sUser = SessionContext.getCurrentSession().getUserName();
        
        Bean bean = new Bean();
        bean.put("FIRST_NAME", "John");
        bean.put("LAST_NAME", "Doe");
        bean.put("EMAIL", "email@domain.com");
        bean.put("PROFILE_IMAGE", FileUtil.getContent(ResourceUtil.getResourceAsStream("/images/" + sUser.toLowerCase() + ".png")));
        
        return bean;
    }
}
</file>

This object must be [[jvx:server:lco:inject_objects|injected]] in your session LCO, for example via ServiceLoader. If it's injected, the API call

<file java>
((ProjX)getApplication()).getDynamicContent("userDetails");
</file>

will return the Bean instance of your DynamicUserContent.

As you can see, it's super easy to inject an object and make it accessible in your application without changing your application code.